Hi guys, Do you know if M1 chip implements the EL3 or not? What's the ARM spec for it, ARMV8-A or more precision for the extension version like v8.x-A? PS: I am very curious about the M1 name, where does this name 'M1' comes from?

I have a piece of code which can be build successfully in xcode 10.x version, but today the code build failed after I grade the xcode to 11.1 version, so I want to see if there's xcode version macro can be used in build phase, like this:#if XCODE_SDK_MAJ_VERSION <11 code line 1 code line 2#else code line 2#endifAny comments?

The RN of macOS 11 beta 6 said that "In macOS 11 and later, the kernel doesn’t load a kext if an equivalent System Extension solution exists. You may continue to use kexts in macOS 10.15 and earlier" The equivalent System Extension is so subjective, how to understand the exact meaning of the 'equivalent' here with a little bit objective syntax? IOW: what's the essential indicator of the 'equivalent' between the sysext and kext?

Hello,I am wondering if there's kind of way that can be used to avoid the generation of the panic file...The backgroud is we develop a kext and it panics on some machines, but there's no any panic file created in the /Library/Logs/DiagnosticReports folder, interesting we do see the pop up window saying "Your computer encounters issue... More details or Ignore" like this, the panic content will display in the text area of the popup, but no panic file created

For example, I am using the macOS 10.14.6, BuildVersion: 18G95. I encounter a panic when load my kext, so I want to see which kernel function result in this panic through the backtrace info, I can get the .dSYM of my kext, but how can I get the .dSYM of the release kernel of the system of I am using?

We have a main kext project(as A for short), also we have another project(B) mostly provide the basic utilitis to the main kext project A. We want to build the B as a static library file B.a, then add the B.a to the A project. But seems it doesn't work: first we can't build the B.a project (it's a kext project as origin). So my question is, for this case, do we need to create a framework from B and use it in A? can a kext link with a static lib file?@eskimo, any comments?